home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group93c.txt
/
000004_icon-group-sender _Thu Jul 1 13:56:09 1993.msg
< prev
next >
Wrap
Internet Message Format
|
1994-02-02
|
1KB
Received: from owl.CS.Arizona.EDU by cheltenham.CS.Arizona.EDU; Thu, 1 Jul 1993 15:46:42 MST
Received: by owl.cs.arizona.edu; Thu, 1 Jul 1993 15:46:40 MST
Date: Thu, 1 Jul 93 13:56:09 PDT
From: alex@laguna.Metaphor.COM (Bob Alexander)
Message-Id: <9307012056.AA00256@laguna.Metaphor.COM>
To: icon-group@cs.arizona.edu
Subject: Re: Tables versus lists
Status: R
Errors-To: icon-group-errors@cs.arizona.edu
Just a couple of comments:
Last time I looked at the implementation, copy(L) creates a non-linked
version of list L, at least until the next time you extend it. Depending
on the dynamics of a program, it's possible that the expense of copying
a list might pay off, since all subsequent list accesses would be as
fast as they could ever be.
Disadvantages: it takes twice the space of the list, momentarily, to
make the copy and, or course, it takes time to copy it. Also,
reliance on "undocumented" behavior such as this can result in
surprises in the future.
Although tables are implemented very nicely, remember that additional
space is required for keys and hash info.
-- Bob Alexander
Metaphor Computer Systems (415) 966-0751 alex@metaphor.com
====^=== Mountain View, CA ...{uunet}!{decwrl,apple}!metaphor!alex